    TAPE CONTENTS AND INSTRUCTIONS TO BRING UP CONGEN AND GENOA
    -----------------------------------------------------------



The following files are on the enclosed 9-track tape, saved using the
BACKUP program -- 800 BPI, interchange mode:


congen.rel
draw.rel
edits.rel
genera.rel
genoa.rel
glbld.rel
imbed.rel
prune.rel
stereo.rel
xmn.rel
amnacd.lib
bmterp.lib
bsterp.lib
congen.lib
isopre.lib
surv.lib
tsterp.lib
init.cg0
init.gli
deppex.mac
bcplib.rel



To bring up CONGEN and GENOA:
-----------------------------

1. Login to the directory (ppn) on which you want the CONGEN and GENOA
files to be. Restore the files from the tape to this directory.


2. Make a file called deppex.mac containing the following externals:

    MAKDEV	The SIXBIT representation of the device upon which the 
		CONGEN (and GENOA) files are stored (e.g., SIXBIT /DSKB/)

    MAKPPN	The PPN of the account under which the CONGEN files are
		stored (e.g., XWD 122,1015)

    SAVEXT	The SIXBIT representation of the extension which the
		runnable CONGEN files will have (e.g., SIXBIT /SHR/)

A sample deppex.mac is included in the files on the tape, but you should
use this as a guide only - the actual values for MAKDEV, MAKPPN and
SAVEXT need to be specified for each different TOPS10 installation.
3. Assemble deppex.mac with MACRO (result: deppex.rel):

    .r macro

    *deppex_deppex

    NO ERRORS DETECTED

    PROGRAM BREAK IS 000003
    CPU TIME USED 00:00.208

    15P CORE USED

    *^Z


4. Separately link (with deppex) and save the following modules:

	congen.rel, draw.rel, edits.rel, genera.rel, genoa.rel,
	glbld.rel, prune.rel, imbed.rel, stereo.rel, xmn.rel

The link step is demonstrated by the following sequence for linking the
congen module. For the other modules, the appropriate module name should
be substituted where "congen" now appears:

    .r link
    *deppex,congen
    */s bcplib
    */g

After each module is linked, save the resulting core image as the
runnable file whose extension is as specified by SAVEXT in the
deppex.mac file (e.g. congen.shr). The core image has a sharable high
segment and a user-specific low segment.


5. CONGEN and GENOA are now ready to be run; to the TOPS10 monitor, type

	ru congen

and CONGEN should respond with

	WELCOME TO CONGEN...

or type

	ru genoa

and GENOA should respond with

	WELCOME TO GENOA...
NOTES
-----

The CONGEN module is the main one (i.e., the one which the user should
RUN) for the CONGEN program, and the GENOA module is the main one for
the GENOA program. These programs utilize the runnable modules by
chaining with the RUN UUO and communicating intermediate results on
files.

During the running of CONGEN (and GENOA), temporary files with names
nnnTOP.CG, nnnSTR.CG, nnnSC1.CG, nnnSC2.CG and (if the recording option
is chosen) nnnREC.CG are created, where nnn is the job number.  If
CONGEN is exitted normally, all of these files are cleaned up, but in
the event of a ^C exit, they are left intact.  This is both a benefit
and a drawback; a benefit because at any time the user can abort an
unexpectedly lengthy computation by issuing a ^C, then RUNning CONGEN
again (this is a general escape mechanism in the program, and will
always be safe to do), at which point CONGEN will pick up all pertinent
information from the files; a drawback because the files stay around
even if the user does not RUN CONGEN again - they may clutter up the
directory, and may lead to some confusion if someone later logs in and
gets the same job number (in this case, RUN CONGEN will put the user
back in the middle of the session stored on the .CG files; you can
always tell when this has happened, because you don't get the normal
greeting message, but just the prompt #).
